neuron Algo Follow Insurer Experience API icon

neuron Algo Follow Insurer Experience API

(0 reviews)

Authentication πŸ”

πŸ›‘οΈ Overview

This page explains how to securely access the Insurer Experience API, including authentication using JWT (OAuth 2.0) and Client ID Enforcement, as well as connection-level security and credential access.

The Insurer Experience API enforces a strict security model to ensure confidentiality, integrity, and controlled access to all resources.

All requests must:

  • Use HTTPS/TLS 1.2+
  • Include a valid JWT bearer token or a valid Client ID
  • Use port 443

Unencrypted HTTP connections are not supported.


🌐 Transport & Network Security

TLS Requirements

To ensure confidentiality and integrity:

  • Only TLS 1.2 or higher is allowed.
  • Plain HTTP or downgraded SSL connections are rejected.

Port Requirements

To reach Neuron service endpoints:

  • Outbound access to port 443 is required.
  • Firewalls and proxies may require updates to allow communication.

πŸ”‘ JWT Validation (OAuth 2.0)

The Insurer Experience API supports OAuth 2.0 using JWT Bearer tokens for authentication.

Include the token in every request:

Authorization: Bearer <access_token>

Identity Provider

Neuron integrates with Azure Active Directory (Azure AD) using a Multi-Tenant Application Model.

Token Validation Rules

The API gateway verifies:

ClaimRequirementPurpose
audMust match API audienceEnsures token is intended for Neuron
rolesMust include required rolesEnforces access authorization
tenantIdMust match onboarding configurationValidates organisation-level access
expMust be unexpired (max 60 min)Limits token misuse
SignatureMust match Azure AD JWKSEnsures token integrity

Error Handling

Invalid tokens return:

401 Unauthorized
Error: Invalid Token

πŸ” JWT Validation Flow (Sequence Diagram)

Below is the full authentication and validation workflow, including token issuance, JWKS retrieval, caching, and downstream API invocation.

resources/neuron_jwt_flow-cc84cf36-363b-4085-bbc2-ee82df3337cc.png


🧾 Client ID Enforcement

For APIs configured to use Client ID Enforcement, requests must include:

client_id: <your-client-id>

Refer to the Getting Started guide for how to obtain your client_id.

Error Handling

When the client ID is missing or invalid:

401 Unauthorized
Error: Invalid Client Id

🧡 Accessing JWT Credentials

To obtain JWT credentials for your application:

  1. Contact the Neuron Operations & Support Team.
  2. Provide your environment details and intended API usage.
  3. The team will issue access details and onboarding instructions.

Support Contact:

tbd


Reviews